When you run a risk analysis project in SAS^® Risk Dimensions^®, the project might fail while pricing the portfolio. The following message is reported in the SAS log:

This issue is known to occur on the PowerPC architecture on the AIX operating system when a method contains a large number of SAS statements. The large number is likely tens of thousands or more. There is a hardware limitation that can prevent SAS from traversing a large number of the lines of source code that are generated while executing the SAS statements.

The workaround is to sufficiently reduce the number of SAS statements used in the method. Due to the nature of how the lines of source code are generated, it is not possible to estimate the maximum number of SAS statements that can be used. However, in one test case, this issue occurred when using 140,000 SAS statements in a single method.

Note that the "Segmentation Violation In Task [ RISK ]" message is generic and is not necessarily caused by this issue. To help verify whether you have encountered this particular cause, you can test by replicating and running the risk analysis project in a different operating environment.

For additional guidance to troubleshoot other possible causes of the "Segmentation Violation In Task [ RISK ]" message, see Troubleshooting SAS® Risk Dimensions®.

For information about obtaining a fix that circumvents this issue in release 5.2_M1 of SAS Risk Dimensions, contact SAS Technical Support.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS Risk Dimensions Enterprise Edition	64-bit Enabled AIX	5.2_M1	6.3	9.2 TS2M0	9.4 TS1M3

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

---

A fix for this issue for SAS Threaded Kernel Core Routines 9.3_M2 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/I29.html#53952

---

Many SAS statements inside a single method is one of several possible causes of the error message, "Segmentation Violation In Task [ RISK ]", when you run a PROC RISK step.

Type:	Problem Note
Priority:	high

Date Modified:	2014-09-17 03:07:51
Date Created:	2014-08-20 06:45:16